Jump to content

Video Decoding Support for the Dragonwing EVK Board

From RidgeRun Developer Wiki


Follow us on: YouTube Twitter LinkedIn Email Share this page

Share This Page




IQ-9075 can decode H.264 and H.265 with software-based and hardware-accelerated elements. Use v4l2h264dec and v4l2h265dec for hardware-accelerated video decoding. Using the hardware-accelerated codecs can free in average between 2% and 7% of the CPU load, depending on the video resolution.

Problems running the pipelines shown on this page? Please see our GStreamer Debugging guide for help.


Info
The following tests were done with an IMX577 camera connected to the Dragonwing IQ-9075 EVK

Video Decoding

These elements are supported for the Ubuntu Image (Ubuntu 24.04.04) and files with a 1080p resolution generated in the last section were used to test average performance and element latency.

CPU Decoders

These are the supported CPU Decoders for the Dragonwing EVK Board:

  • avdec_h264
    • Example pipeline for the avdec_h264 element:
gst-launch-1.0 -v filesrc location=avdec_h264-test.mp4 ! qtdemux ! h264parse ! avdec_h264 ! waylandsink
  • Performance measurements for the avdec_h264 element:
Resolution %MEM RSS (KB) GPU Utilization (%) FPS Mean FPS CPU Usage (%)
1280x720 0.2 86240 0.88 29.990 30.092 6
1920x1080 0.3 118548 1.70 30.005 30.098 6
3840x2160 0.9 328588 1.69 29.988 30.057 11
  • avdec_h265:
    • Example pipeline for the avdec_h265 element:
gst-launch-1.0 -v filesrc location=avdec_h265-test-test.mp4 ! qtdemux ! h265parse ! avdec_h265 ! waylandsink
  • Performance measurements for the avdec_h264 element:
Resolution %MEM RSS (KB) GPU Utilization (%) FPS Mean FPS CPU Usage (%)
1280x720 0.2 96436 0.59 15.942 18.275 7
1920x1080 0.3 133392 0.00 10.307 12.072 8
3840x2160 1.0 372048 0.00 2.903 4.309 2
  • avdec_mpeg4
  • avdec_mpeg2video
  • avdec_vp8
  • avdec_vp9

VPU Decoders

These are the supported Hardware Accelerated Decoders for the Dragonwing EVK Board.

  • v4l2h264dec
    • Example pipeline for the v4l2h264dec element:
 gst-launch-1.0 -e -v filesrc location=v4l2h264dec.mp4 ! qtdemux ! h264parse ! v4l2h264dec ! waylandsink
  • Performance measurement forthe v4l2h264dec element:
Resolution %MEM RSS (KB) GPU Utilization (%) FPS Mean FPS CPU Usage (%)
1280x720 0.1 41484 0.76 30.000 30.102 4
1920x1080 0.1 41580 1.44 29.987 30.102 5
3840x2160 0.1 42116 1.44 30.011 30.096 4
  • v4l2h265dec
    • Example pipeline for the v4l2h265dec element:
gst-launch-1.0 -e -v filesrc location=v4l2h265dec.mp4 ! qtdemux ! h265parse ! v4l2h265dec ! waylandsink
  • Performance measurements for the v4l2h265dec element:
Resolution %MEM RSS (KB) GPU Utilization (%) FPS Mean FPS CPU Usage (%)
1280x720 0.1 48576 1.55 30.000 30.103 4
1920x1080 0.1 48696 1.45 29.996 30.101 4
3840x2160 0.1 49168 1.45 30.003 30.100 4

FAQ

Why use an explicit hardware decoder instead of decodebin?
decodebin can select a software decoder. Explicit pipeline definition is best for ensuring hardware-accelerated decoding.
Can IQ-9075 decode H.265 4K@30 fps video?
Yes, when using the v4l2h265dec hardware-accelerated element. The software-based avdec_h265 element decodes 4K video but can't keep up with the 30 fps, providing a mean framerate of 4.3 fps in our results.

Related pages

Cookies help us deliver our services. By using our services, you agree to our use of cookies.